Skip to content

Rename Redlio Designs to Redlio Labs and refresh the profile - #2247

Open
mayursinh1211 wants to merge 3 commits into
remoteintech:mainfrom
mayursinh1211:rename-redlio-designs-to-redlio-labs
Open

Rename Redlio Designs to Redlio Labs and refresh the profile#2247
mayursinh1211 wants to merge 3 commits into
remoteintech:mainfrom
mayursinh1211:rename-redlio-designs-to-redlio-labs

Conversation

@mayursinh1211

@mayursinh1211 mayursinh1211 commented Aug 9, 2026

Copy link
Copy Markdown

The company listed as Redlio Designs rebranded to Redlio Labs. Same company, same team, same registration; only the name and domain changed, and redliodesigns.com redirects to redliolabs.com.

I work with the company, so this is a first-party update rather than a drive-by correction.

Renaming src/companies/redlio-designs.md to redlio-labs.md so the filename matches the new slug, per CONTRIBUTING.

What changed and why

Field Before After
title / slug Redlio Designs Redlio Labs
website redliodesigns.com redliolabs.com
careers_url redliodesigns.com/career redliolabs.com/careers
Office locations Ahmedabad and Jamnagar Full Ahmedabad address
technologies javascript, php javascript, react, nodejs, postgres, nosql, php, python
  • The old careers_url was broken twice over. It pointed at the old domain, and /career returns 404 on the new domain too. The live path is /careers.
  • The blurb and service list described work the company no longer offers (web design, e-commerce builds, digital marketing, SEO). Replaced with its current five services.
  • Jamnagar has been removed from office locations. The working office is Ahmedabad.
  • LinkedIn link updated to the current company slug.

region, remote_policy and company_size are unchanged.

Checks

  • node .github/scripts/validate-companies.js src/companies/redlio-labs.md passes with 0 errors and 0 warnings.
  • npm run build succeeds on Node 22 (per .nvmrc) and renders /companies/redlio-labs/ correctly.

Two things for maintainers

  1. addedAt / updatedAt are left untouched, since CONTRIBUTING says maintainers manage them. The rendered page currently reads "Last updated: November 4, 2024", which is now inaccurate given the rewrite. Happy to bump updatedAt if you would rather I did.
  2. /companies/redlio-designs/ will start 404ing. You may want a redirect to the new path, since the old URL has been indexed since 2024. I did not add one as I do not know your preferred mechanism.

Update

Two additions at the company's request, pushed in a second commit:

  • ## Office locations now carries the full office address rather than the city alone.
  • ## How to apply names the three currently open roles. Your format has no field for individual vacancies, and none of the other company files list them, so these sit in the prose. careers_url remains the authoritative source and the text says so. If you would rather profiles stayed role-agnostic, say the word and I will drop the list and leave the careers link to do the work.

Validator still reports 0 errors and 0 warnings, and the site still builds on Node 22.

The company rebranded from Redlio Designs to Redlio Labs. Same company,
same team, same registration; the name and domain changed and
redliodesigns.com now redirects to redliolabs.com.

Renames the file so the slug matches the current name, and corrects the
details that went stale with the rebrand:

- website and careers_url move to redliolabs.com. The old careers_url
  pointed at /career, which 404s on both the old and the new domain;
  the live path is /careers.
- blurb and service list replaced with the company's current five
  services. The previous list (web design, e-commerce, digital
  marketing, SEO) describes work it no longer offers.
- LinkedIn link updated to the current company slug.
- Jamnagar removed from office locations. It is a former address; the
  office is Ahmedabad.
- technologies updated to the stack actually used today.
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

Thanks for your contribution!

The following issues were found with your company profile(s). Please fix them and push an update to this PR:

src/companies/redlio-designs.md

  • ❌ Could not read file: ENOENT: no such file or directory, open 'pr-head/src/companies/redlio-designs.md'

See the company profile format docs for reference.

@mayursinh1211

Copy link
Copy Markdown
Author

The failing validate check is not about the new file. It is the rename, and I think it is a gap in the workflow rather than something I can fix from this PR.

validate-companies.yml builds its file list from gh pr diff --name-only, which for a rename includes both paths, then checks out the PR head with sparse-checkout and validates each one:

MAPPED_FILES+=("pr-head/$f")

src/companies/redlio-designs.md is deleted by this PR, so it does not exist in the head checkout and readFileSync returns ENOENT. Any PR that renames or removes a company file will fail the same way.

src/companies/redlio-labs.md, the file this PR actually adds, validated clean. It is absent from the bot comment because the reporting loop skips files with no errors and no warnings, and I get 0 errors / 0 warnings running the script locally:

$ node .github/scripts/validate-companies.js src/companies/redlio-labs.md
"summary": { "total": 1, "passed": 1, "failed": 0, "warnings": 0 }

One way to fix it, if useful: skip paths that are not present in the checkout, in the mapping loop.

[ -f "pr-head/$f" ] || continue

Or filter the changed-file list to added and modified entries via gh api .../files and its status field.

Happy to open that as a separate issue or PR if you would like it fixed properly rather than waved through. And if you would rather avoid the rename entirely, I can rewrite this as an in-place edit to redlio-designs.md, though the slug would then keep the old company name.

mayursinh1211 and others added 2 commits August 9, 2026 13:44
On the company's instruction: the office locations section now carries
the full Ahmedabad address rather than the city alone, and the how to
apply section names the three roles that are currently open.

The careers link stays the authoritative source, since it always
reflects the live list.
@mayursinh1211

Copy link
Copy Markdown
Author

A quick follow-up on this one. The rename is still current on our side, and I have just pushed a small commit updating the office address to its current form.

The failing validate-companies check remains the workflow gap described above (the renamed file is looked up at its old path in the PR head). Happy to adjust anything if a maintainer prefers a different approach, including the in-place edit offered earlier. Thanks for your time.

@dougaitken

Copy link
Copy Markdown
Member

Thanks for this, and for the diagnosis of the failing check — you were right on both counts. I've confirmed it independently: gh pr diff --name-only returns both paths on a rename, and the deleted one isn't in the pr-head checkout, so readFileSync throws. Nothing for you to fix. I've opened #2255 to fix the workflow itself, taking the gh api / status approach you suggested over the -f guard, since a bare existence check would also mask a genuinely missing file.

I also re-ran the validator against your head commit and it reports 1 passed, 0 errors, 0 warnings — so the file is fine.

I checked your URL claims and they all hold up: redliodesigns.com redirects to redliolabs.com, /careers is live, /career 404s on the new domain, and the LinkedIn slug resolves. Appreciate the detail in the writeup — it made this quick to verify.

Three things I'll handle on the maintainer side, so no action needed from you:

  • The redirect you asked about. We use a redirectFrom frontmatter field for exactly this — see src/companies/cloudbees.md for the Codeship rename. I'll add /companies/redlio-designs/ and /redlio-designs, which also preserves the auto-generated legacy redirect.
  • updatedAt — you were right to leave it; I'll bump it.
  • The three named vacancies — I'll take you up on your offer and drop them. Profiles here stay role-agnostic so they don't go stale, and careers_url already does that job.

One thing I'd like your read on before I merge.

The region field is about where a company will hire someone, not where it sells — it drives the browse facets, so worldwide puts the profile on /browse/worldwide/ alongside companies that hire anywhere on earth.

The old profile's remote status read "Possibility to remote work — from home or an office." The new one reads "The team works from the Ahmedabad office, and each open role lists its location", and all three roles you listed are Ahmedabad-based. Read plainly, that describes an office-based company, which makes region: worldwide look wrong now.

remote_policy: hybrid is a valid value here and I'm not questioning the listing — hybrid companies are welcome. I just want the region facet to be accurate.

So: can someone outside Gujarat, or outside India, actually be hired into these roles?

  • If yes, the remote status wording undersells it and should say so explicitly.
  • If no, region should be asia-pacific, and I'd rather set that than have someone in Berlin filter to "Worldwide" and find a role they can't take.

Your call on which reflects reality — you're first-party here and I'd rather ask than assume. Once you confirm, I'll make the edits above and merge.

@mayursinh1211

mayursinh1211 commented Sep 8, 2026 via email

Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants